BLOCKCHAIN / TOKEN CERTIFICATION
Federation servers require token-signing certificates to prevent attackers from altering or counterfeiting security tokens in an attempt to gain unauthorized access to federated resources.
The private/public key pairing that is used with token-signing certificates is the most important validation mechanism of any federated partnership because these keys verify that a security token was issued by a valid partner federation server and that the token was not modified during transit.
Token-signing certificate requirements
A token-signing certificate must meet the following requirements to work with AD FS:
For a token-signing certificate to successfully sign a security token, the token-signing certificate must contain a private key.
The AD FS service account must have access to the token-signing certificate's private key in the personal store of the local computer. This is taken care of by Setup. You can also use the AD FS Management snap-in to ensure this access if you subsequently change the token-signing certificate.
What is a Token Certification?
It is a public and official document that certifies that a Token, Wallet or blockchain database contains certain information and its information is transferred to a third person, who receives it with a certificate, which ensures the content received.
Its main function is to publicly guarantee the truth, integrity and content of the information contained in a token, blockchain or wallet.
"Fingerprints" of the data
INTERCER calculates a specific cryptographic hash, or "fingerprint," for each file.
This hash is an algorithm that produces the same result when the input file is exactly the same, which is useful for verifying its authenticity.
Any change to the input file, however minimal, creates a radically different fingerprint.
The hashing algorithm has been designed to work in one direction only, making it impossible to determine the original entered file from the resulting hash code, shielding the process from tampering.